Estimating, like anything in software development, is a skill. And it's HARD.

Estimates are invaluable for us to project plan.

I think misunderstanding what's in an estimate is a big reason so many devs hate estimating.

Snippets are powerful. This one little tool can reduce toil and make it easier to follow your team's style conventions. They're also fun to play with. Work smarter not harder!

I see teams choose to forgo estimates when they find them challenging and don't see value in them. But there's a ton of value in team estimates!

I loathe loathe loathe dependency management. Updating dependencies sounds simple but it's something we're not usually taught. This is the post I wish I had when I was learning how to do this.

Asking for help is a skill like anything else. The better you get at how you ask questions, the better your team and senior engineers will be able to support you–and the more quickly you will level up.

Estimating is HARD but it's a skill that you can hone like any other, such as coding or professional communication.

When I'm working with a new team, a question that comes up often is "What info should I include in my PR description?" A good PR description can open doors to quicker and more productive PR reviews.

Code review is an integral part of most teams' workflows. But knowing exactly what to look at while you're reviewing a team member's code or how to organize your thoughts can be hard.